Skip to content

DOCS: lstk migration guide - #873

Open
quetzalliwrites wants to merge 4 commits into
mainfrom
docs-97-migration-guide-lstk
Open

DOCS: lstk migration guide #873
quetzalliwrites wants to merge 4 commits into
mainfrom
docs-97-migration-guide-lstk

Conversation

@quetzalliwrites

Copy link
Copy Markdown
Collaborator

Peter authored this migration guide for lstk, it's ready for review.

Closes: https://linear.app/localstack/issue/DOC-97/docs-migration-guide-for-legacy-cli-new-lstk

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Aug 18, 2026

Copy link
Copy Markdown

Deploying localstack-docs with  Cloudflare Pages  Cloudflare Pages

Latest commit: a91b3b5
Status: ✅  Deploy successful!
Preview URL: https://dd35e741.localstack-docs.pages.dev
Branch Preview URL: https://docs-97-migration-guide-lstk.localstack-docs.pages.dev

View logs

@quetzalliwrites

Copy link
Copy Markdown
Collaborator Author

@remotesynth I've added it to the current subsection of dev tools for now. (Since we want to update the lstk doc and add a new subsection, we'll need to revise where the migration guide best belongs.

@remotesynth remotesynth left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Made a few suggestions

Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk-migration.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk-migration.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk-migration.mdx Outdated
Comment thread src/content/docs/aws/developer-tools/running-localstack/lstk-migration.mdx Outdated
Co-authored-by: Brian Rinaldi <brianrinaldi@fastmail.com>
@quetzalliwrites

quetzalliwrites commented Aug 19, 2026

Copy link
Copy Markdown
Collaborator Author

allrighty @peter-smith-phd brian already left his review, so I incorporated his suggestions into your PR already

right now, it looks like there's just one last feedback comment for you :)

@peter-smith-phd

Copy link
Copy Markdown
Contributor

Given that I wrote this, I won't provide any addition review feedback.

But, I did notice that it's not showing up in the preview pages. How would the users find this page?

image

Replace the separate Homebrew/npm code blocks with a Tabs component,
matching the pattern used elsewhere in the lstk docs, per review
feedback.
@quetzalliwrites

quetzalliwrites commented Aug 25, 2026

Copy link
Copy Markdown
Collaborator Author

Pushed 0e8fd4f9 converting the Homebrew/npm install commands to a Tabs component, per Brian's suggestion.

Now checking Peter's concern about the page not showing in nav....

@quetzalliwrites

Copy link
Copy Markdown
Collaborator Author

Given that I wrote this, I won't provide any addition review feedback.

But, I did notice that it's not showing up in the preview pages. How would the users find this page?

image

It's not showing up because you didn't update the astro config js @peter-smith-phd

Copy link
Copy Markdown
Contributor

Ummm… just a reminder that I wrote the page in Notion, and somebody else converted it to the localstack-docs format 😛

Register the new lstk migration guide in the Developer Tools >
Running LocalStack section, between the lstk CLI and MCP Server
entries.
@quetzalliwrites

Copy link
Copy Markdown
Collaborator Author

You asked why it wasn't showing up, I understood your question to be about not understanding how it works ;) @peter-smith-phd

@quetzalliwrites

Copy link
Copy Markdown
Collaborator Author

@remotesynth do you want to add anything? otherwise, can you approve the PR to remove merging blocker?

This looks good to merge tmw if agreed.

@quetzalliwrites
quetzalliwrites requested review from peter-smith-phd and removed request for peter-smith-phd August 25, 2026 19:10
@quetzalliwrites

Copy link
Copy Markdown
Collaborator Author

Heads up, pinging you here too @mmaureenliu in case you'd like to review now that you're back tmw.

Copy link
Copy Markdown
Contributor

I definitely understand how it works, but I recommend you say "It's not showing up because the astro config js wasn't updated correctly" or "thanks for pointing that out, I'll fix it", rather than indicating that it was me that missed it in the first place. Just a different language choice.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants